Hi @klaraloreen
Thank you for contributing to the Opencast Admin UI.
We noticed that you have not yet filed an Individual Contributor License Agreement. Doing that (once) helps us to ensure that Opencast stays free for all. If you make your contribution on behalf of an institution, you might also want to file a Corporate Contributor License Agreement (giving you as individual contributor a bit more security as well). It can take a while for this bot to find out about new filings, so if you just filed one or both of the above do not worry about this message!
Please let us know if you have any questions regarding the CLA.

EDIT(@lkiesow ): Klara did submit an ICLA to Apereo. It usually takes a while for Apereo to process the submissions. Meanwhile, please ignore the ICLA test and point reviewers to this comment if anyone asks on further pull requests.

Use docker or podman to test this pull request locally.

Run test server using develop.opencast.org as backend:

podman run --rm -it -p 127.0.0.1:3000:3000 ghcr.io/opencast/opencast-admin-interface:pr-1196

Specify a different backend like stable.opencast.org:

podman run --rm -it -p 127.0.0.1:3000:3000 -e PROXY_TARGET=https://stable.opencast.org ghcr.io/opencast/opencast-admin-interface:pr-1196

It may take a few seconds for the interface to spin up.
It will then be available at http://127.0.0.1:3000.
For more options you can pass on to the proxy, take a look at the README.md.

This pull request is deployed at test.admin-interface.opencast.org/1196/2025-05-22_14-37-07/ .
It might take a few minutes for it to become available.

Looks good for pagination. But I found another problem:

• The select all checkbox keeps being selected after starting an action (Select all → Action → Start Task → e.g. run „Republish Metadata“)

Hi @klaraloreen, thanks for your work.
I like the idea of providing the state val and checked props, however this would (I assume) only uncheck the header as written in the title. But we should also cover the deselection of the selected items, so I introduce the mechanism (in a method) here: #1286
There, I use ref to target the header checkbox too!
So, I would recommend going as follows:

• Wait for Deselect table rows when sorting #1286 to be merged first & rebase to this PR.
• No using state & checked props! in favor of reusing the method in sync mode!
• Use the deselect method also in place related to pagination!

Thanks & BR

This pull request has conflicts ☹
Please resolve those so we can review the pull request.
Thanks.

Hi @ferishili, thanks for your improvements! I removed the state variable and used the deselect method instead, just like you suggested.

Thanks, @klaraloreen,
it works as expected, however, it would also make sense to force that deselection on the page number dropdown.
What do you think?

[UPDATE]: It is decided; the correct way in terms of UX is to deselect all items even when we change the number of rows per page, therefore, we need to take care of that!
PS: as soon as this change is also pushed to the PR, it is good to go!

Hi @ferishili, thanks for your suggestion! I added the method to force deselection on change of the page size. Sorry for the late reply!